I have a hyper-v environment and I setup AD and wds which is configured and it has an install image and a boot image. I do have the server vm and the regular windows 10 vm on the same network with static addresses and my server vm has the wsd AD and dhcp roles installed. The windows 10 vm wont pxe boot even though i set that up in wds to any and all clients and i included an unattended.xml file. any ideas?

8 Spice ups

The client VM has to be DHCP and on the same physical network segment as server (absent some extra configuration which you wouldn’t do in a lab environment).

If WDS is on THE SAME server as DHCP, from WDS Right click the server, properties. On the DHCP tab, check both “dont listen on port 67” and “configure option 60” - While you’re in properties, under PXE response tab check respond to all clients (you can adjust later once you know it works).

PXE works via DHCP, client broadcasts for DHCP, and a second broadcast for boot server info. One of the above being misconfigured is your issue.

1 Spice up

So don’t use static up addresses, I thought you had to. Do I have to install server role dhcp and active directory services?

I thought you said you had AD/DCHP on this server already?
The VM with AD/DHCP on it SHOULD have a Static address. The PXE client VM should get its address/dns settings from DHCP.
Clarify: You have a VM with WDS on it. Do you have an AD/DHCP server VM? And if so, is WDS installed on it also?

As of now I have Ed’s setup with a install and boot image. I took out the static address. Every YouTube video I see to deploy via PXE via Ed’s does not have static setup. Do I need to setup static again PXE one hyper v never seems to work for me. Not sure why. Do you have a preferred video for me to watch for this.

Did you configure the DHCP scope options for client boot? Examples such as 60, or 66/67.

by “windows 10 vm” do you mean a blank VM that you want to deploy win 10 on?

How does the win 10 vm have a static ip address? when it boots to pxe it will use dhcp - does it get an ip when booting to pxe mode?

Hi it is a windows 10 vm it is via dhcp. I can only PXE boot via hyper v gen 1 but no address is generated

PXE = Pre-Boot Execution Environment.

Your client (the Win10 VM) would normally not get/use an IP until after the OS boots. On a physical machine, you’d hit F12 or the like to initiate a network boot immediately after power on.

I don’t have Hyper-V handy but I do believe you can specify the VM to network boot in the VM’s settings from the Hyper-V manager console.